-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.1.0 #89
Conversation
…4/occupi into feature/biometrics
Bringing changes downstream
…orking test for rate limiter
Feat/backend/rate limit api
Defining action to run on push to develop branch as well
Update lint-test-build-golang.yml
…&-integration-testing All possible tests were written and pass
…oking Feat/mobile integration/booking
chore: Remove unused mobile test workflow
Linting errors solved
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
11908971 | Triggered | Generic Password | a6a08ae | occupi-backend/tests/handlers_test.go | View secret |
11908971 | Triggered | Generic Password | d23e629 | occupi-backend/tests/handlers_test.go | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Description
Facilitating a v0.1.0 release
Fixes # (issue)
Type of change
Please delete options that are not relevant.
N/A
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
N/A
Checklist:
Please have a look at the changelog of the corresponding version number to see what new features have been added